ci(java): auto-release the Maven Central deployment#323
Conversation
publishToMavenCentral only stages the Central Portal deployment (state stays VALIDATED, needs a manual Publish click). Use publishAndReleaseToMavenCentral so the release completes automatically — 0.18.0 had to be released by hand.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe non-dry-run Gradle publish command in the Java publishing workflow is changed from ChangesMaven Central Publish Task
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Problem
The 0.18.0 Java release uploaded to Maven Central but stayed in VALIDATED state — never published — requiring a manual "Publish" click in the Central Portal.
Cause
publish-java.ymlran./gradlew publishToMavenCentral, which only stages the Central Portal deployment. The vanniktech plugin's separatepublishAndReleaseToMavenCentraltask is the one that uploads and releases.Fix
Switch the publish step to
publishAndReleaseToMavenCentral. Future Java releases publish automatically.(Gradle config in
build.gradle.ktsis unchanged; the task name carries the release semantics.)Note
0.18.0 itself still needs a one-time manual Publish in the Central Portal (the VALIDATED deployment) — this fix prevents the manual step for 0.18.1+.
Summary by CodeRabbit